This talk would walk through compliance steps from the perspective of a good faith effort to create open source software -- in other words, what most people need to do if they are going to publish their software as open source and stick it on GitHub/GitLab in a public repository. This is the most common use case, but is little talked about. Most people do not want to do anything special to monetize OSS or retain special control. This is probably even the most common scenario for companies and universities, and is basically what all independent community projects do.
But much of what we talk about as FOSS lawyers is how to deal with rabbit holes; like CLA's, relicensing, distribution of source with compiled binaries, media devices, hardware drivers, etc.... New lawyers or compliance engineers get overwhelmed by those talks and think they need to do more work then they do before they open source their first project.
Unlike many talks on the topic, this talk aims to show what is normal. It would also be talking about what you normally would not try to do or worry about: for example, special liability clauses, jurisdiction selection clauses, or being forced to provide free support.
This talk would be a useful jumping off point for lawyers or business leaders who look at how long licenses (i.e. how many pages of words) are, get intimidated, over-think things, and then never do actually open source anything -- to everyone's detriment. This would be aimed at lawyers who are encountering open source licenses for the first time -- and just want to not screw it up.